This chapter describes how to troubleshoot the SpinServer by using the sensors commands and system messages. It also describes how to obtain and send support information to Network Appliance Technical Support.
If a SpinServer malfunctions, verify that its physical environment (for instance, power and temperature) is within operational limits. For information on environmental operating limits, see the Installation Guide for your hardware platform. The SpinServer includes a number of sensors that track the physical environment; use the sensors commands to gather information from the sensors.
If there is an environmental problem with the SpinServer, correct the situation as needed. For instance, if the SpinServer is in a facility in which the ambient temperature is too high, increase the air flow and cooling in the facility. If a SpinServer component such as a fan fails, contact Network Appliance Technical Support.
Use the sensors temp show command to display temperature information about one or more SpinServers. The command has the following syntax:
sensors temp show [-ssid spinserver -key sensor_ID]
The following example displays warnings and information about the operating temperature of the motherboard and CPU in a SpinServer enclosure.
spinserver::> sensors temp show
Host Name Sensor ID Sensor Description Temperature (Celsius)
sserv10 7-10 CPU 1 Temperature 38
sserv10 7-11 Motherboard Temperature 2 40
sserv10 7-12 CPU 2 Temperature 41
sserv10 7-9 Motherboard Temperature 1 42
Use the sensors fan show command to display information about the intake, exhaust, and CPU fans in one or more SpinServers. The command has the following syntax:
sensors fan show [-ssid spinserver -key fan_ID]
The following example displays information about the operational performance of the intake, exhaust, and CPU fans in a SpinServer cluster.
spinserver::> sensors fan show Host Name Fan ID Fan Description Speed (RPM) Server1 7-4 Chassis Intake Fan 2 2250 Server1 7-8 CPU 2 Fan 5113 Server1 7-5 Chassis Intake Fan 3 2250 Server1 7-7 CPU 1 Fan 5152 Server1 7-6 Chassis Intake Fan 4 2250 Server1 7-1 Chassis Exhaust Fan 1 2860 Server1 7-2 Chassis Exhaust Fan 2 0 Server1 7-3 Chassis Intake Fan 1 2250 Server12 7-3 Chassis Intake Fan 1 2250 Server12 7-4 Chassis Intake Fan 2 2109 Server12 7-1 Chassis Exhaust Fan 1 2860 Server12 7-7 CPU 1 Fan 4591 Server12 7-8 CPU 2 Fan 4821 Server12 7-6 Chassis Intake Fan 4 2250 Server12 7-2 Chassis Exhaust Fan 2 0 Server12 7-5 Chassis Intake Fan 3 2250
Use the sensors power show command to display voltage information about a SpinServer's motherboard and CPU. The command has the following syntax:
sensors power show [-ssid spinserver -key sensor_ID]
The following example displays warnings and information about the power of the motherboards and CPUs in a SpinServer cluster.
spinserver::> sensors power show Host Name Sensor ID Sensor Description Voltage Server1 33 3.3 Volt Supply 3.3712 Server1 12 12.0 Volt Supply 12.1875 Server1 CPU CPU Core Voltage 1.4382 Server1 50 5.0 Volt Supply 5.044 Server2 33 3.3 Volt Supply 3.3712 Server2 50 5.0 Volt Supply 5.018 Server2 12 12.0 Volt Supply 12.1875
Use the sensors ups show command to display information about a SpinServer's uninterruptible power supply (UPS). The command has the following syntax:
sensors ups show [-ssid spinserver]
The following example displays information about the operational performance of the UPSs in a SpinServer cluster.
spinserver::> sensors ups show
SpinServer ID Utility Power Off Last Battery Minutes
Line Threshold Change Date Left
Voltage
ss1 117 15 05/22/01 73
ss2 117 15 05/22/01 104
If a SpinServer fails, support personnel can request crash information to assist with diagnosis and repair. To obtain crash information, use the system crashdumps show command. The command has the following syntax:
system crashdumps show -ssid spinserver -name file_name
The following example displays information about a crash file named vmdump.1 on a SpinServer named Server1:
spinserver::> system crashdumps show -ssid Server1 -name vmdump.1 SpinServer ID Server1 FileName vmdump.1 Build 35372 Creation Date 1/14/03 11:34:11 AM EST Size 1077510144 Last Modified 1/14/03 11:35:29 AM EST Readable true Writeable true Compression Method Not Compressed Encryption Method Not Encrypted
Use this command only with the assistance of support personnel.
You can delete a crash file by using the system crashdumps delete command. The command has the following syntax:
system crashdumps delete -ssid spinserver -name file_name
The following example deletes a crash file named vmdump.1 on a SpinServer named Server1:
spinserver::> system crashdumps delete -ssid Server1 -name vmdump.1
Use this command only at the direction of support personnel.
If you contact Network Appliance Technical Support for assistance, support personnel can request that you submit support-related information from one or more SpinServers. The spinservers sendsupportinfo command enables you to send support information to Technical Support via email or FTP. Use this command at the direction of support personnel.
The command has the following syntax:
spinservers sendsupportinfo -ssid spinserver -type {email | ftp} -parameters parameters
The value of the -parameters parameter varies according to the value of the -type parameter. If the value of the -type parameter is specified as email, specify parameters of the form email_server, email_id1, email_id2, etc. If the value of the -type parameter is specified as ftp, specify a parameter of the form FTP_URL.
The following example sends support information from a SpinServer named Server1 to the FTP URL ftp://ftp.spinnakernet.com/incoming:
spinserver::> spinservers sendsupportinfo -ssid Server1 -type ftp -parameters ftp://ftp.spinnakernet.com/incoming
To view system messages, use the methods described in the SpinFS 2.5 Messages and Troubleshooting Guide. This document also includes a complete listing of messages that can be generated by a SpinServer system.
If the cause of a problem is not apparent from the system messages, contact Network Appliance Technical Support.
If the spinservers joincluster command fails with the error message Timed out after 30 waiting for the RDB online indication, verify that the network is configured and running correctly (for instance, ensure that the Ethernet switch is configured). Use the ping command to test connectivity to the SpinServer whose cluster is being joined. For the argument of the ping command, use the IP address specified by the value of the spinservers joincluster command's -clusternodeipaddress parameter. If you are using an MTU setting of 9000, specify the -s 9000 parameter on the ping command to use a 9000-byte packet:
# ping [-s 9000] spinserver_IP_address
After the SpinServer chassis has been replaced, the identification information that is stored in the NetBIOS on the motherboard of the SpinServer is updated.
The serial number of a SpinServer is unique to each SpinServer chassis and is stored in the NetBIOS on the motherboard of the SpinServer chassis.
After the field-replaceable units, including the SCSI disk drives, are installed in the replacement chassis and the chassis is mounted in the rack, power up the SpinServer. The SpinFS software checks the serial number for accuracy and automatically deletes the old serial number and writes the new serial number for the replacement chassis into the management software.
To display the new serial number, navigate to the SpinServer → Show node in the SpinManager GUI. The new serial number is displayed.
The asset tag for a SpinServer is linked to the serial number. After the SpinServer chassis is replaced, the asset tag is no longer recognized by the system and is deleted from the management software.
For your equipment identification purposes, the previous asset tag or a new asset tag can be used to identify the SpinServer. To add the asset tag, navigate to the SpinServer → Show node in the SpinManager GUI. The new serial number is displayed. Enter the asset tag in the Asset Tag field, then click Modify.
Copyright © 2004 Network Appliance, Inc.; copyright © 2003, 2004 Spinnaker Networks, LLC. All rights reserved. Specifications subject to change without notice.